Description

This PR addresses the issue with upgrade failing to update permissions of a new volume if only uid is set due to an incorrect chown command (see linked ticket for more details).

I have also updated a piece of code responsible to disabling remote access (e.g. to a wizard) to tolerate "not found" errors for authorities to ensure reentrability - otherwise if a later call (e.g. deleting a trusted cluster) fails due to etcd error, the authorities won't be there and it'll fail with not found.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Linked tickets and other PRs

• Refs [BUG] Upgrade fails if new volume specifies uid without gid #1788.

TODOs

• Self-review the change
• Write tests
• Perform manual testing
• Address review feedback

Testing done

Install a cluster, then upgrade to a new version that has this volume:

 nodeProfiles:
   - name: worker
     description: Worker
     requirements:
       volumes:
         - name: data
           path: /var/data
           targetPath: /data
           uid: 3000

Before the change, upgrade fails with:

User Message: failed to execute phase "/bootstrap"
	failed to run {[chown 3000: /var/data] setting ownership of /var/data to 3000: false}:
		exit status 1] handler:upgrade utils/logging.go:103

After the change, the upgrade passes and volume is chown'd:

ubuntu@node-1:~/upgrade$ ls -l /var | grep data
drwxr-xr-x  3 3000 root   4096 May 28 00:05 data